General best practices for balancing developer velocity with containment, supervision, and least privilege.

A pattern for building personal knowledge bases using LLMs.

This is an idea file, it is designed to be copy pasted to your own LLM Agent (e.g. OpenAI Codex, Claude Code, OpenCode / Pi, or etc.). Its goal is to communicate the high level idea, but your agent will build out the specifics in collaboration with you.

Most people's experience with LLMs and documents looks like RAG: you upload a collection of files, the LLM retrieves relevant chunks at query time, and generates an answer. This works, but the LLM is rediscovering knowledge from scratch on every question. There's no accumulation. Ask a subtle question that requires synthesizing five documents, and the LLM has to find and piece together the relevant fragments every time. Nothing is built up. NotebookLM, ChatGPT file uploads, and most RAG systems work this way.

Claude Code over-comments. It narrates loops, restates signatures, leaves change-log notes addressed to a PR reviewer who'll never see them, and points at spec sections that have already moved. Two layers fix it and compound: a pre-hoc layer in CLAUDE.md that steers the model as it writes, and a post-hoc cleanup skill that reclaims the residue — plus everything verbose you inherited from past work and other contributors. Use both; neither is sufficient alone.

The whole thing is one principle applied twice. Code shows how. A comment earns its place only by carrying why — a non-obvious constraint, a deliberate deviation, a gotcha, a workaround, the reason a tempting simpler version is wrong. Everything else is restatement, and restatement rots: it drifts out of sync, adds diff noise, and trains readers to skim past comments entirely.

The block I use:

This guide will show you how to compile and install the legacy Nvidia driver on Debian. The steps bellow are compatible with both nvidia-legacy-340xx-driver and nvidia-legacy-390xx-driver and can be installed on Debian 13 (Trixie) as well as Debian 12 (Bookworm) or Debian 11 (Bullseye) in both 64-bit and 32-bit version. Execute the lines one by one and wait for every line to finish before proceeding to next. Only the lines starting with sudo should be executed as root. The lines with sudo pbuilder will take a lot of time.

To install the nvidia-legacy-390xx-driver version replace 340xx with 390xx everywhere bellow.
To install both 64-bit and 32-bit libraries for wine/steam you should run Step 2. twice.
It was confirmed that this method also works with the nvidia-tesla-470-driver version.

Update, upgrade and install the required packages.

A guide how to get and activate Windows 8, 8.1, 10 and 11 Pro for free!

If you see the Windows keyboard button in this guide; and you can't find it on your keyboard, you likely have/had Windows 10 which has the button . If you can't find that one, you likely have a PC that has been upgraded to Windows 8/8.1/10/11 from Windows 8.1/8/7/Vista/XP and other ones. If you have one of those, refer the Windows key button to as yours. A list of them is below:

- Windows 11

- Windows 10

• Do not subscribe to every service at once. Most free credits expire quickly. Test them one by one and move to the next when your current credits run out.
• Register, verify your account, and claim your credits. Follow each platform's documentation to connect your coding tools.
• Keep your API keys private. Do not share them publicly. (save or star this gist for future update)

1. Open the document in Google Docs
2. Scroll to the bottom of the document, so all the pages are present
3. Open Developer Tools on separate window and choose the Console tab
4. Paste the code
5. Have fun!